-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[9.100.x-prod] SRVLOGIC-299 SRVLOGIC-266 SRVLOGIC-185 - Update Go Image 1.21; Bundles Update; Manager Config set #46
[9.100.x-prod] SRVLOGIC-299 SRVLOGIC-266 SRVLOGIC-185 - Update Go Image 1.21; Bundles Update; Manager Config set #46
Conversation
…ge 1.21; Bundles Update; Manager Config set Signed-off-by: Ricardo Zanini <[email protected]>
Signed-off-by: Ricardo Zanini <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have added some minor comment regarding the usage of ubi8 vs ubi9 in case it could make sense.
arguments to pass to the builder\nARG MAVEN_ARGS_APPEND\n\n# Copy from build context | ||
to skeleton resources project\nCOPY --chown=1001 . ./resources\n\nRUN /home/kogito/launch/build-app.sh | ||
./resources\n \n#=============================\n# Runtime Run\n#=============================\nFROM | ||
registry.access.redhat.com/ubi8/openjdk-17-runtime:latest\n\nENV LANG='en_US.UTF-8' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ricardozanini Just a reminder to double-check. In 9.99.x-pod (i.e., previous release), it looks like we used
registry.access.redhat.com/ubi9/openjdk-17:latest instead.
see:
Line 11 in 5325a42
Runtime Run\n#=============================\nFROM registry.access.redhat.com/ubi9/openjdk-17:latest\n\nENV |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
talking to my self.... after seen the image names provided by @rgdoliveira .
If produtized DI and JS images are on rhel8....
registry.redhat.io/openshift-serverless-1/logic-jobs-service-postgresql-rhel8:1.33.0
maybe ubi8 is the correct choice here.
Anyway, just forget my comment if don't make sense.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was ubi9, but yeah I'm downgrading to align and avoid problems.
@@ -16,7 +16,7 @@ RUN /home/kogito/launch/build-app.sh ./resources | |||
#============================= | |||
# Runtime Run | |||
#============================= | |||
FROM registry.access.redhat.com/ubi9/openjdk-17:latest | |||
FROM registry.access.redhat.com/ubi9/openjdk-17-runtime:latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
regarding my previous comment, here we have ubi9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's fine this one is upstream.
@@ -16,7 +16,7 @@ RUN /home/kogito/launch/build-app.sh ./resources | |||
#============================= | |||
# Runtime Run | |||
#============================= | |||
FROM registry.access.redhat.com/ubi9/openjdk-17:latest | |||
FROM registry.access.redhat.com/ubi8/openjdk-17-runtime:latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ubi8 here, IDK, just a reminder
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one is midstream.
@@ -15,7 +15,7 @@ | |||
- schema_version: 1 | |||
name: "operator-builder" | |||
version: "1.33.0" | |||
from: "registry.access.redhat.com/ubi8/go-toolset:1.20.12" | |||
from: "registry.access.redhat.com/ubi8/go-toolset:1.21" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here, ubi8.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's midstream.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ricardozanini I've suggested the correct prod images tags.
bundle.prod/manifests/logic-operator-rhel8-controllers-config_v1_configmap.yaml
Outdated
Show resolved
Hide resolved
bundle.prod/manifests/logic-operator-rhel8-controllers-config_v1_configmap.yaml
Outdated
Show resolved
Hide resolved
bundle.prod/manifests/logic-operator-rhel8-controllers-config_v1_configmap.yaml
Outdated
Show resolved
Hide resolved
bundle.prod/manifests/logic-operator-rhel8-controllers-config_v1_configmap.yaml
Outdated
Show resolved
Hide resolved
bundle.prod/manifests/logic-operator-rhel8-controllers-config_v1_configmap.yaml
Outdated
Show resolved
Hide resolved
bundle.prod/manifests/logic-operator-rhel8-controllers-config_v1_configmap.yaml
Outdated
Show resolved
Hide resolved
Also something that is missing for the bundle is the annotations for infra feature tests, same thing you did for OSL 1.32 in Jira SRVLOGIC-245, can you please also add that in this PR? |
Signed-off-by: Ricardo Zanini <[email protected]>
Description of the change:
Comprehends:
Motivation for the change:
Since we have now the newly Go 1.21 image officially, we can make it easier by just upgrading our base image:
https://catalog.redhat.com/software/containers/ubi8/go-toolset/5ce8713aac3db925c03774d1?architecture=amd64&image=66452129e206ab012dc21031
Additionally, I've upgraded the JDK images and set to ubi8 for ubiquiteness.
@rgdoliveira @domhanak can you please inform/confirm the image tags for these, so I can update the PR?
Checklist
How to backport a pull request to a different branch?
In order to automatically create a backporting pull request please add one or more labels having the following format
backport-<branch-name>
, where<branch-name>
is the name of the branch where the pull request must be backported to (e.g.,backport-7.67.x
to backport the original PR to the7.67.x
branch).Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.